Information verification method and related device

ABSTRACT

An information verification method and a related device. The method includes: receiving, by a first profile server, a remote profile management request sent by a remote profile management server, where the remote profile management request includes a first profile owner identifier; obtaining a second profile owner identifier in profile information; determining whether the first profile owner identifier is the same as the second profile owner identifier; and sending a remote profile management command to user equipment when the first profile owner identifier is the same as the second profile owner identifier. In this way, a loss caused to an operator or a profile owner due to a user&#39;s access to an invalid network or random profile unlocking is avoided, network security is improved, and waste of network resources is reduced.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a National Stage of International Patent ApplicationNo. PCT/CN2017/099267 filed on Aug. 28, 2017, which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments relate to the field of wireless network technologies, and inparticular, to an information verification method and a related device.

BACKGROUND

Currently, a user may purchase a subscriber identity module (SIM) from acommunications operator, to obtain a number resource of the operator, soas to be entitled to use a communications service provided by theoperator. As technologies and requirements evolve, an embedded universalintegrated circuit card (eUICC), also referred to as an embedded SIM(eSIM), emerges. The eUICC is a newly defined secure element that isused by a plurality of communications operators to remotely manage asubscriber, and is placed into a terminal in a plug-in manner or awelding manner. A user may select an operator network for user equipment(UE) of the user, and download a profile from the operator network.After the profile is downloaded to the eUICC, the user equipment mayaccess the selected operator network by using data provided in theprofile. In addition, the user may alternatively select anotheroperator, and download a profile of the another operator to implement ascenario such as a handover between the operator networks. Becauseinternet of things exists in different industries, it is relativelyconvenient to provide an eUICC for a device in the internet of things,so that the device accesses and uses the network. For example, it ismore convenient for a device such as a smart meter or a smart in-vehiclesystem to use an eUICC to be connected to and authenticated by thenetwork and to use the network. Many international and national standardorganizations are formulating related standards for an eUICC, mainlyincluding Global System for Mobile Communications Association (GSMA) andEuropean Telecommunications Standards Institute (ETSI).

In an existing eUICC architecture, the following function definitionsare provided: An integrated circuit card identifier (ICCID) is alsoreferred to as a profile ID, and is used to uniquely identify a profile.An eUICC identifier (EID) is used to uniquely identify an eUICC. Aprofile is a set of file structures, data, applications, and the like,and includes one or more network access applications and correspondingnetwork access credentials, for example, an international mobilesubscriber identity and a personal key identity ( ). A subscriptionmanager-data preparing (SM-DP, or Subscription Manager Data Preparation+(SM-DP+)) server is also referred to as a profile provisioner or aprofile download server, and may create, generate, manage, or transmit aprofile based on basic subscription information, such as aninternational mobile subscriber identity (IMSI), provided by a mobilenetwork operator (MNO). After a profile is downloaded to an eUICC, anMNO may send a remote profile management (RPM) command to manage thedownloaded profile, for example, perform operations such as activating,deactivating, deleting, and enumerating an installed profile list andupdating a profile-related parameter. However, only a profile owner (PO)has permission to manage the downloaded profile, and whether the MNO isan owner of the profile is not verified. Consequently, a networksecurity problem easily occurs in a network profile management process.

SUMMARY

An information verification method and a related device, to resolve anetwork security problem is described with possible embodiments.

According to a first aspect, an embodiment provides an informationverification method, including: first receiving, by a first profileserver, a remote profile management request sent by a remote profilemanagement server, and obtaining a second profile owner identifier inprofile information; then determining whether a first profile owneridentifier is the same as the second profile owner identifier; andsending, by the first profile server, a remote profile managementcommand to user equipment when the first profile owner identifier is thesame as the second profile owner identifier. This prevents a third partyfrom maliciously tampering with profile information that is notpossessed by the third party, and avoids a loss caused to an operator ora profile owner due to a user's access to an invalid network or randomprofile unlocking. In addition, the profile server verifies a PO on anetwork side. In this way, network security can be improved, abidirectional authentication process between the profile server and aterminal can be reduced, and a waste of network resources can bereduced.

In an implementation, the first profile server may obtain the secondprofile owner identifier in the profile information from a local memory,or read the second profile owner identifier in the profile informationfrom a storage area of another connected server.

In another implementation, the first profile server may send a firstrequest to the user equipment, where the first request is used to obtainthe second profile owner identifier. After receiving the first request,the user equipment sends, to the first profile server, the profileinformation that carries the second profile owner identifier.

In another implementation, the first profile server may send a secondrequest to a second profile server, where the second request is used toobtain the second profile owner identifier. After obtaining the secondprofile owner identifier corresponding to the PO, the second profileserver sends, to the first profile server, the profile information thatcarries the second profile owner identifier.

In another implementation, after receiving the remote profile managementrequest sent by the remote profile management server, the first profileserver may perform verification or identification by using informationsuch as a message header field and an initiator certificate that are inthe message sent by the remote profile management server to the firstprofile server and that are used to identify an initiator, and a profileowner identifier (PO ID) that is carried in the remote profilemanagement request thereby ensuring identity validity of the remoteprofile management server.

In another implementation, the first profile server may compare thefirst profile owner identifier with the second profile owner identifierto verify whether the first profile owner identifier is the same as thesecond profile owner identifier.

In another implementation, when the first profile owner identifier isdifferent from the second profile owner identifier, the first profileserver sends a response message to the remote profile management server,where the response message is used to notify the remote profilemanagement server of a verification error.

In another implementation, the first profile owner identifier and thesecond profile owner identifier each include at least one of thefollowing: a profile owner identifier that is identifiable to the firstprofile server, or a profile owner identifier that is identifiable tothe second profile server.

In another implementation, when the first profile owner identifierincludes only the profile owner identifier that is identifiable to thefirst profile server, the profile owner identifier that is identifiableto the first profile server in the first profile owner identifier needsto be separately compared with the profile owner identifier that isidentifiable to the first profile server in the profile information andthe profile owner identifier that is identifiable to the second profileserver in the profile information, to verify whether the profile owneridentifier that is identifiable to the first profile server in the firstprofile owner identifier is the same as a profile owner identifier inthe profile information. If the profile owner identifier that isidentifiable to the first profile server in the first profile owneridentifier is the same as a profile owner identifier in the profileinformation, it is determined that the first profile owner identifier isthe same as the second profile owner identifier, or if the profile owneridentifier that is identifiable to the first profile server in the firstprofile owner identifier is different from any profile owner identifierin the profile information, it is determined that the first profileowner identifier is different from the second profile owner identifier.When the first profile owner identifier includes only the profile owneridentifier that is identifiable to the second profile server, averification method is the same as the foregoing method. Details are notdescribed herein again for the sake of brevity. When the first profileowner identifier includes both the profile owner identifier that isidentifiable to the first profile server and the profile owneridentifier that is identifiable to the second profile server, theprofile owner identifier that is identifiable to the first profileserver in the first profile owner identifier and the profile owneridentifier that is identifiable to the second profile server in thefirst profile owner identifier need to be respectively compared with theprofile owner identifier that is identifiable to the first profileserver in the profile information and the profile owner identifier thatis identifiable to the second profile server in the profile information.Only when the profile owner identifier that is identifiable to the firstprofile server in the first profile owner identifier is the same as theprofile owner identifier that is identifiable to the first profileserver in the profile information and the profile owner identifier thatis identifiable to the second profile server in the first profile owneridentifier is the same as the profile owner identifier that isidentifiable to the second profile server in the profile information, itis determined that the first profile owner identifier is the same as thesecond profile owner identifier.

In another implementation, the first profile server obtains anidentifier correspondence list when the first profile owner identifieris different from the second profile owner identifier, where theidentifier correspondence list includes a correspondence between aprofile server identifier and a profile owner identifier, determineswhether a profile owner identifier corresponding to the first profileowner identifier exists in the identifier correspondence list, and sendsthe remote profile management command to the user equipment when theprofile owner identifier corresponding to the first profile owneridentifier exists in the identifier correspondence list, to furtherverify the PO.

In another implementation, the first profile server obtains theidentifier correspondence list from the remote profile managementserver, obtains the identifier correspondence list from the secondprofile server, or obtains the identifier correspondence list from thelocal memory.

In another implementation, the profile owner identifier includes aprofile server identifier and a profile owner identifier.

In another implementation, because the first profile owner identifierincludes a profile server identifier and a profile owner identifier, thesecond profile owner identifier that is identifiable to the firstprofile server in the profile information may be obtained based on anidentifier of the first profile server included in the first profileowner identifier. Alternatively, the second profile owner identifierthat is identifiable to the second profile server in the profileinformation is obtained based on an identifier of the second profileserver included in the first profile owner identifier.

In another implementation, the first profile server is a serverconfigured to manage a profile, and the second profile server is aserver configured to download the profile.

According to a second aspect, an embodiment provides an informationverification method, including: receiving, by user equipment, a remoteprofile management command sent by a first profile server, where theremote profile management command includes a first profile owneridentifier; obtaining a second profile owner identifier in profileinformation; then determining whether the first profile owner identifieris the same as the second profile owner identifier; and finallyexecuting the remote profile management command when the first profileowner identifier is the same as the second profile owner identifier.This prevents a third party from maliciously tampering with profileinformation that is not possessed by the third party, and avoids a losscaused to an operator or a profile owner due to a user's access to aninvalid network or random profile unlocking. In addition, the profileserver verifies a PO on a network side. In this way, network securitycan be improved, a bidirectional authentication process between theprofile server and a terminal can be reduced, and a waste of networkresources can be reduced.

In an implementation, the user equipment may first search for the secondprofile owner identifier in the profile information based on an ICCID(profile identifier) carried in the remote profile management command,and compare the first profile owner identifier with the second profileowner identifier to verify whether the first profile owner identifier isthe same as the second profile owner identifier.

In another implementation, before receiving the remote profilemanagement command sent by the first profile server, the user equipmentreceives an update message sent by a remote profile management server ora second profile server, where the update message includes an identifierof the first profile server and a corresponding profile owneridentifier.

In another implementation, after receiving the update request sent bythe remote profile management server or the second profile server, theuser equipment may perform verification or identification may beperformed by using information such as a message header field and aninitiator certificate that are in the update message and that are usedto identify an initiator, and the PO ID that is carried in the updatemessage, thereby ensuring identity validity of the remote profilemanagement server or the second profile server.

In another implementation, the first profile owner identifier includesat least one of the following: a profile owner identifier that isidentifiable to the first profile server or a profile owner identifierthat is identifiable to the second profile server.

In another implementation, the user equipment obtains an identifiercorrespondence list when the first profile owner identifier is differentfrom the second profile owner identifier, where the identifiercorrespondence list includes a correspondence between a profile serveridentifier and a profile owner identifier, determines whether a profileowner identifier corresponding to the first profile owner identifierexists in the identifier correspondence list, and executes the remoteprofile management command when the profile owner identifiercorresponding to the first profile owner identifier exists in theidentifier correspondence list.

In another implementation, before receiving the remote profilemanagement command sent by the first profile server, the user equipmentreceives a first request sent by the first profile server, where thefirst request is used to obtain the second profile owner identifier, andsends, to the first profile server, the profile information that carriesthe second profile owner identifier.

In another implementation, the user equipment may send a responsemessage to the first profile server or the remote profile managementserver when the first profile owner identifier is different from thesecond profile owner identifier, where the response message is used tonotify the remote profile management server of a verification error.

According to a third aspect, an embodiment provides an informationverification method, including: sending, by a remote profile managementserver, a remote profile management request to a first profile server,where the remote profile management request includes a first profileowner identifier, and the remote profile management request is used toinstruct the first profile server to determine whether a second profileowner identifier in profile information is the same as the first profileowner identifier; and sending a remote profile management command touser equipment when the second profile owner identifier is the same asthe first profile owner identifier. This prevents a third party frommaliciously tampering with profile information that is not possessed bythe third party, and avoids a loss caused to an operator or a profileowner due to a user's access to an invalid network or random profileunlocking. In addition, the profile server verifies a PO on a networkside. In this way, network security can be improved, a bidirectionalauthentication process between the profile server and a terminal can bereduced, and a waste of network resources can be reduced.

In an implementation, the remote profile management server determineswhether the first profile server configured to manage a profile and asecond profile server previously configured to download the profile area same server, and when the first profile server and the second profileserver are different servers, the remote profile management serverdetermines a profile owner identifier that is identifiable to the firstprofile server or a profile owner identifier that is identifiable to thesecond profile server.

In another implementation, the remote profile management server mayconfigure information about the first profile server in the profileinformation in advance, and also configure the profile owner identifierthat is identifiable to the first profile server, and after completingthe configuration, send an update message to the user equipment, wherethe update message includes an identifier of the first profile serverand a corresponding profile owner identifier.

In another implementation, the first profile owner identifier includesthe identifier of the first profile server and a corresponding profileowner identifier that is identifiable to the first profile server, or anidentifier of the second profile server and a corresponding profileowner identifier that is identifiable to the second profile server.

According to a fourth aspect, an embodiment provides a first profileserver. The first profile server is configured to implement the methodand the functions that are performed by the first profile server in thefirst aspect. The first profile server is implemented by usinghardware/software. The hardware/software of the first profile serverincludes units corresponding to the foregoing functions.

According to a fifth aspect, an embodiment provides user equipment. Theuser equipment is configured to implement the method and the functionsthat are performed by the user equipment in the second aspect. The userequipment is implemented by using hardware/software. Thehardware/software of the user equipment includes units corresponding tothe foregoing functions.

According to a sixth aspect, an embodiment provides a remote profilemanagement server. The remote profile management server is configured toimplement the method and the functions that are performed by the remoteprofile management server in the third aspect. The remote profilemanagement server is implemented by using hardware/software. Thehardware/software of the remote profile management server includes unitscorresponding to the foregoing functions.

According to a seventh aspect, an embodiment provides another firstprofile server, including a processor, a memory, and a communicationsbus. The communications bus is configured to implement connection andcommunication between the processor and the memory, and the processorexecutes a program stored in the memory, to implement the steps in theinformation verification method provided in the first aspect.

In an implementation, the profile server provided in an embodiment mayinclude a corresponding module configured to perform behavior of theprofile server in the foregoing method. The module may be softwareand/or hardware.

According to an eighth aspect, an embodiment provides other userequipment, including a processor, a memory, and a communications bus.The communications bus is configured to implement connection andcommunication between the processor and the memory, and the processorexecutes a program stored in the memory, to implement the steps in theinformation verification method provided in the second aspect.

In an implementation, the user equipment provided in an embodiment mayinclude a corresponding module configured to perform behavior of theuser equipment in the foregoing method. The module may be softwareand/or hardware.

According to a ninth aspect, an embodiment provides another remoteprofile management server, including a processor, a memory, and acommunications bus. The communications bus is configured to implementconnection and communication between the processor and the memory, andthe processor executes a program stored in the memory, to implement thesteps in the information verification method provided in the thirdaspect.

In an implementation, the remote profile management server provided inan embodiment may include a corresponding module configured to performbehavior of the remote profile management server in the foregoingmethod. The module may be software and/or hardware.

According to a tenth aspect, an embodiment provides a computer-readablestorage medium, and the computer-readable storage medium stores aninstruction. When the instruction runs on a computer, the computer isenabled to perform the methods in the foregoing aspects.

According to an eleventh aspect, an embodiment provides a computerprogram product including an instruction. When the computer programproduct runs on a computer, the computer is enabled to perform themethods in the foregoing aspects.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments or in thebackground more clearly, the following briefly describes theaccompanying drawings required for describing the embodiments or thebackground, in which:

FIG. 1 is a schematic structural diagram of an information verificationsystem according to an embodiment;

FIG. 2A is a schematic flowchart of an information verification methodaccording to an embodiment;

FIG. 2B is a schematic flowchart of another information verificationmethod according to an embodiment;

FIG. 3 is a schematic flowchart of an information verification methodaccording to an embodiment;

FIG. 4 is a schematic flowchart of an information verification methodaccording to another embodiment;

FIG. 5A is a schematic flowchart of an information verification methodaccording to still another embodiment;

FIG. 5B is a schematic flowchart of an information verification methodaccording to still another embodiment;

FIG. 6 is a schematic flowchart of an information verification methodaccording to yet another embodiment;

FIG. 7 is a schematic structural diagram of a first profile serveraccording to an embodiment;

FIG. 8 is a schematic structural diagram of user equipment according toan embodiment;

FIG. 9 is a schematic structural diagram of a remote profile managementserver according to an embodiment;

FIG. 10 is a schematic structural diagram of another first profileserver according to an embodiment;

FIG. 11 is a schematic structural diagram of other user equipmentaccording to an embodiment; and

FIG. 12 is a schematic structural diagram of another remote profilemanagement server according to an embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

The following describes the embodiments with reference to theaccompanying drawings in the embodiments.

FIG. 1 is a schematic structural diagram of an information verificationsystem according to an embodiment. The information verification systemincludes a profile server, a RPM server, and UE. The profile server mayinclude at least one of a SM DP (or SM-DP+) server and a subscriptionmanager discovery server (SM-DS). The SM DP+ is an enhanced release ofan SM DP server, and is collectively referred to as the SM DP+ below.The SM-DP+ is mainly configured to generate, based on basic subscriptioninformation (for example, an international mobile subscriber identity)provided by the remote profile management server, a profile that can bedownloaded to an eUICC, and the SM-DS is mainly configured to provideone or more SM DP+ addresses for the user equipment. The remote profilemanagement server may be an MNO, an mobile virtual network operator(MVNO) that purchases and uses a profile provided by an MNO, or anenterprise operation and maintenance server that uses a profile providedby an MNO. For example, a company such as BMW Group or State Grid mayconfigure, for a customer or an employee of the company, a profilemanagement service required for connecting a network. The user equipmentmay include an eUICC and a local profile assistant (LPA) module. TheeUICC may be embedded in the user equipment, or may be a pluggable eUICCinserted into the user equipment. Alternatively, the eUICC may beimplemented by using an eUICC that is embedded in a chip and that isaccessed by using a bus. The LPA module is configured to manage profiledownloading, and provide a UI interface (for example, a profileinstallation list) for the user equipment, so that a user can manage(activate, deactivate, delete, or unlock) a local profile in the eUICC.In addition, the user equipment may further retrieve an EID and/or anICCID by using the LPA module. The LPA module may be a virtual logicmodule, or may be an entity module, for example, a field programmablegate array. The LPA includes a local discovery service (LDS), localprofile download (LPD), and a local user interface user interface (LUI).The LPA in the user equipment and the LPA in the eUICC may each includeone or more of the LDS, the LPD, and the LUI.

Based on the foregoing architecture of the information verificationsystem, a PO may send a remote profile management command to the SM DP+or a managing SM DP+ to manage a downloaded profile. During managementof the downloaded profile, it is possible that the profile is previouslydownloaded by using an SM DP+, and then the profile in the eUICC ismanaged by using another SM DP+(for example, Managing SM DP+). If the SMDP+ configured to manage the profile and the SM DP+ configured todownload the profile are different servers, an identifier of themanaging SM DP+ needs to be first updated to a profile-relatedparameter, such as profile metadata and profile information(ProfileInfo), and then the managing SM DP+ is permitted to send aremote profile management command.

As shown in FIG. 2A, when an SM DP+ configured to manage a profile andan SM DP+ configured to download the profile are a same server, the SMDP+ and an eUICC authenticate each other, and the SM DP+ and an MNOauthenticate each other. Both an MNO1 and an MNO2 have permission tomanage the eUICC. However, it is not verified whether the MNO1 and theMNO2 manage respective profiles in the eUICC, either. As shown in FIG.2B, when an SM DP+ configured to manage a profile and an SM DP+configured to download the profile are different servers, the SM DP+ mayassign different PO IDs to a same PO; and the SM DP+ may assign a samePO ID to different POs. For example, an SM DP+ of China Mobile in Chinaassigns a PO ID 46001, and an SM DP+ of China Mobile abroad assigns a POID CMCC. Alternatively, T-Mobile assigns a PO ID 23430, and EE alsoassigns the PO ID 23430. In this case, it is not verified whether anMNO1 and an MNO2 manage respective profiles in an eUICC, either. Becausea PO is not verified, a third party may maliciously tamper with data ina profile. This affects network security. To resolve the problem, thefollowing solutions are proposed.

FIG. 3 is a schematic flowchart of an information verification methodaccording to an embodiment. In this embodiment, a profile serverconfigured to manage a profile and a profile server configured todownload the profile are a same server. The method includes but is notlimited to the following steps.

S301. A remote profile management server sends a remote profilemanagement (RPM) request to a profile server. The RPM request includes afirst PO ID, and the RPM request further includes at least one of anEID, a ICCID, and RPM command-related information.

The first profile owner identifier may include only a profile owneridentifier, or may include a profile server identifier and a profileowner identifier. The profile owner identifier may vary with aimplementation. For example, an MNO and an SM DP+ may agree on a profileowner identifier in advance, or an MNO and an SM DP+ may use anidentifier of a message initiator between the MNO and the SM DP+ as aprofile owner identifier. For another example, State Grid, serving as acompany, manages a profile purchased by State Grid from the MNO. In thiscase, the first profile owner identifier may include a PO ID assigned bythe MNO or the SM DP+ to State Grid. Alternatively, a MVNO purchases aprofile from the MNO. In this case, the first profile owner identifiermay include a PO ID assigned to the MVNO. This ensures that State Gridor the MVNO manages the profile of State Grid or the MVNO by using theMNO.

Optionally, after receiving the RPM request sent by the RPM server, theprofile server may verify identity validity of the RPM server based on aPO ID carried in the RPM request. In an embodiment, verification oridentification may be performed based on at least one type ofinformation such as a message header field and an initiator certificatethat are in the message sent by the RPM server to the profile server andthat are used to identify an initiator, and the PO ID that is carried inthe RPM request. For example, if the PO ID carried in the RPM request isa PO ID of China Mobile, it is verified whether the initiator of the RPMrequest is China Mobile. If the initiator of the RPM request is notChina Mobile, it is verified that an identity of the initiator isinvalid. If the initiator of the RPM request is China Mobile, it isverified that the identity of the initiator is valid. This prevents athird party from maliciously using the PO ID of China Mobile to managethe profile. In verification on the identity of the initiator, averification operation of determining whether the initiator is a validinitiator, a verification operation of judging whether the initiator isa valid initiator, or the like may be performed.

S302. The profile server obtains a second profile owner identifier inprofile information. The following two optional manners are included.

The first implementation includes the following step:

S302 a. The profile server may obtain the second profile owneridentifier in the profile information from a local memory, or read thesecond profile owner identifier in the profile information from astorage area of another connected server. Further, the second profileowner identifier may be obtained by searching, based on a ICCID carriedin the RPM request, for PO ID information stored in profile-relatedmetadata; or a corresponding profile may be searched for based on theICCID carried in the RPM request, and the second profile owneridentifier of the profile is obtained.

The second implementation includes the following steps.

S302 b. The profile server may send a first request to user equipment,where the first request is used to obtain the second profile owneridentifier, the first request may be a Get ProfileInfo interfacecommand, and the first request may carry at least one of an identifierof a second profile server, an EID, and an ICCID. In an embodiment,after a secure channel is established between the profile server and theuser equipment, the profile server may send the first request to theuser equipment through an ES 8+ or ES 9+ interface between the profileserver and the user equipment.

S302 c. After receiving the first request, the user equipment searchesfor the corresponding profile information based on the ICCID carried inthe RPM request, and after finding the corresponding profileinformation, the user equipment sends, to the profile server, theprofile information that carries the second profile owner identifier.

S303. The profile server determines whether the first profile owneridentifier is the same as the second profile owner identifier.

In an embodiment, the profile server may compare the first profile owneridentifier with the second profile owner identifier to verify ordetermine whether the first profile owner identifier is the same as thesecond profile owner identifier.

S304. The profile server sends an RPM command to the user equipment whenthe first profile owner identifier is the same as the second profileowner identifier, where the RPM command carries the first profile owneridentifier, the EID, and the ICCID.

S305. The profile server sends a response message to the remote profilemanagement server when the first profile owner identifier is differentfrom the second profile owner identifier, where the response message isused to notify the RPM server of a verification error.

S306. After receiving the RPM command, the user equipment determineswhether the first profile owner identifier is the same as the secondprofile owner identifier.

In an embodiment, the user equipment may first search for the secondprofile owner identifier in the profile information based on the ICCIDcarried in the RPM command, and compare the first profile owneridentifier with the second profile owner identifier to verify whetherthe first profile owner identifier is the same as the second profileowner identifier.

S307. The user equipment executes the RPM command when the first profileowner identifier is the same as the second profile owner identifier. Theuser equipment may send a response message to the profile server or theRPM server when the first profile owner identifier is different from thesecond profile owner identifier, where the response message is used tonotify the RPM server of a verification error.

In this embodiment, the profile server, serving as both the serverconfigured to download the profile and the server configured to managethe profile, first receives the RPM request sent by the RPM server, andobtains the second profile owner identifier in the profile information,and then determines whether the first profile owner identifier is thesame as the second profile owner identifier. The profile server sendsthe RPM command to the user equipment when the first profile owneridentifier is the same as the second profile owner identifier. This notonly prevents a third party from maliciously tampering with profileinformation that is not possessed by the third party, but also avoids aloss caused to an operator or a profile owner due to a user's access toan invalid network or random profile unlocking. In addition, the profileserver verifies a PO on a network side. In this way, network securitycan be improved, a bidirectional authentication process between theprofile server and a terminal can be reduced, and a waste of networkresources can be reduced.

FIG. 4 is a schematic flowchart of an information verification methodaccording to another embodiment. In this embodiment, a first profileserver configured to manage a profile and a second profile serverconfigured to download the profile are different servers. The methodincludes but is not limited to the following steps.

S401. An RPM server or the second profile server updates profileinformation to user equipment. This step includes: S401 a. The RPMserver sends an update message to the user equipment. S401 b. The secondprofile server sends an update message to the user equipment. The updatemessage includes an identifier of the first profile server, and mayfurther include a corresponding profile owner identifier.

In an embodiment, the RPM server or the second profile server maypreconfigure information about the first profile server in the profileinformation, and preconfigure a profile owner identifier that isidentifiable to the first profile server. The information about thefirst profile server may include the identifier of the first profileserver.

After the foregoing information is configured, the user equipment may beassigned to the first profile server for remote profile management.Therefore, the RPM server or the second profile server may send theupdate message to the user equipment. The second profile server mayassign a same identifier or different identifiers as PO IDs of a sameprofile owner. Therefore, the PO IDs also need to be updated to theprofile information. For example, if a PO ID assigned by a first SM DP+to China Mobile is 46001, and a PO ID assigned by a second SM DP+ toChina Mobile is CMCC, an identifier of the first SM DP+ and thecorresponding identifier 46001 of China Mobile are stored in the profileinformation, and an identifier of the second SM DP+ and thecorresponding identifier CMCC of China Mobile are also stored in theprofile information, to subsequently search for and verify the PO. Afterreceiving the update message, the user equipment updates the identifierof the first profile server and the corresponding profile owneridentifier to the profile information. Optionally, the RPM server mayfurther configure the identifier of the first profile server and thecorresponding profile owner identifier in the profile information of theuser equipment by using an over-the-air (OTA) message.

Optionally, after receiving the update request sent by the RPM server orthe second profile server, the user equipment may verify identityvalidity of the RPM server or the second profile server based on the POID carried in the update request. In an embodiment, verification oridentification may be performed based on information such as a messageheader field and an initiator certificate that are in the update messageand that are used to identify an initiator, and the PO ID that iscarried in the update message. For example, if the PO ID carried in theupdate request is the PO ID of China Mobile, it is verified whether theinitiator of the update request is China Mobile. If the initiator of theupdate request is not China Mobile, it is verified that an identity ofthe initiator is invalid. If China Mobile is the initiator of the updaterequest, it is verified that the identity of the initiator is valid.Further, the identifier of the first profile server and thecorresponding profile owner identifier are updated to the local profileinformation. This prevents a third party from maliciously using the POID of China Mobile to manage the profile. In verification on theidentity of the initiator, a verification operation of determiningwhether the initiator is a valid initiator, a verification operation ofjudging whether the initiator is a valid initiator, or the like may beperformed.

S402. The RPM server sends an RPM request to the first profile server,where the RPM request includes a first PO ID, and the RPM requestfurther includes at least one of an EID, an ICCID, and RPMcommand-related information, and the first profile owner identifierincludes at least one of the following: a profile owner identifier thatis identifiable to the first profile server or a profile owneridentifier that is identifiable to the second profile server.

The profile owner identifier may vary with a implementation. Forexample, an MNO and an SM DP+ may agree on a profile owner identifier inadvance, or an MNO and an SM DP+ may use an identifier of a messageinitiator between the MNO and the SM DP+ as a profile owner identifier.For another example, State Grid, serving as a company, manages a profilepurchased by State Grid from the MNO. In this case, the first profileowner identifier may include a PO ID assigned by the MNO or the SM DP+to State Grid. Alternatively, a MVNO purchases a profile from the MNO.In this case, the first profile owner identifier may include a PO IDassigned to the MVNO. This ensures that State Grid or the MVNO managesthe profile of State Grid or the MVNO by using the MNO.

Optionally, after receiving the RPM request initiated by the RPM server,the first profile server may verify identity validity of the RPM serverbased on the PO ID carried in the RPM request. In an embodiment,verification or identification may be performed based on informationsuch as a message header field and an initiator certificate that are inthe message sent by the RPM server to the first profile server and thatare used to identify an initiator, and the PO ID that is carried in theRPM request. For example, if the PO ID carried in the RPM request is aPO ID of China Mobile, it is verified whether the initiator of the RPMrequest is China Mobile. If the initiator of the RPM request is notChina Mobile, it is verified that the identity of the initiator isinvalid. If the initiator of the RPM request is China Mobile, it isverified that the identity of the initiator is valid. This prevents athird party from maliciously using the PO ID of China Mobile to managethe profile.

S403. The first profile server obtains a second profile owner identifierin profile information, where the second profile owner identifierincludes at least one of the following: a profile owner identifier thatis identifiable to the first profile server or a profile owneridentifier that is identifiable to the second profile server. Thefollowing two optional manners are included.

The first implementation includes the following steps:

S403 a. The first profile server may send a first request to the userequipment, where the first request is used to obtain the second profileowner identifier, and the first request may be a Get ProfileInfointerface command, and may carry at least one of an identifier of thesecond profile server, an EID, and an ICCID. In an embodiment, after asecure channel is established between the first profile server and theuser equipment, the first profile server may send the first request tothe user equipment through an ES 8+ or ES 9+ interface between the firstprofile server and the user equipment.

S403 b. After receiving the first request, the user equipment searchesfor the corresponding profile information based on the ICCID carried inthe RPM request, and after finding the corresponding profileinformation, the user equipment sends, to the first profile server, theprofile information that carries the second profile owner identifier.

The second implementation includes the following steps.

S403 c. The first profile server may send a second request to the secondprofile server, where the second request is used to obtain the secondprofile owner identifier, and the second request may be a GetProfileInfo interface command, and may carry at least one of anidentifier of the second profile server, an EID, and an ICCID. Theidentifier of the second profile server is used to perform addressing onthe corresponding second profile server, and the EID or the ICCID isused to search for a PO to which the corresponding profile belongs, toobtain the PO ID. For example, the PO may be read from the profileinformation stored in the second profile server, or the second profileserver maintains a plurality of profiles of the RPM server, and searchesfor, based on the ICCID carried in the second request, a PO to which thecorresponding profile belongs, to obtain the PO ID.

S403 d. After obtaining the second profile owner identifiercorresponding to the PO, the second profile server sends, to the firstprofile server, the second profile owner identifier or the profileinformation that carries the second profile owner identifier.

S404. The first profile server determines whether the first profileowner identifier is the same as the second profile owner identifier.

In an embodiment, the first profile server may compare the first profileowner identifier with the second profile owner identifier to verify ordetermine whether the first profile owner identifier is the same as thesecond profile owner identifier.

Further, when the first profile owner identifier includes only theprofile owner identifier that is identifiable to the first profileserver, the profile owner identifier that is identifiable to the firstprofile server in the first profile owner identifier needs to beseparately compared with the profile owner identifier that isidentifiable to the first profile server in the profile information andthe profile owner identifier that is identifiable to the second profileserver in the profile information, to verify whether the profile owneridentifier that is identifiable to the first profile server in the firstprofile owner identifier is the same as a profile owner identifier inthe profile information. If the profile owner identifier that isidentifiable to the first profile server in the first profile owneridentifier is the same as a profile owner identifier in the profileinformation, it is determined that the first profile owner identifier isthe same as the second profile owner identifier. If the profile owneridentifier that is identifiable to the first profile server in the firstprofile owner identifier is different from any profile owner identifierin the profile information, it is determined that the first profileowner identifier is different from the second profile owner identifier.When the first profile owner identifier includes only the profile owneridentifier that is identifiable to the second profile server, averification method is the same as the foregoing method. Details are notdescribed herein again for the sake of brevity. When the first profileowner identifier includes the profile owner identifier that isidentifiable to the first profile server and the profile owneridentifier that is identifiable to the second profile server, theprofile owner identifier that is identifiable to the first profileserver in the first profile owner identifier and the profile owneridentifier that is identifiable to the second profile server in thefirst profile owner identifier need to be respectively compared with theprofile owner identifier that is identifiable to the first profileserver in the profile information and the profile owner identifier thatis identifiable to the second profile server in the profile information.Only when the profile owner identifier that is identifiable to the firstprofile server in the first profile owner identifier is the same as theprofile owner identifier that is identifiable to the first profileserver in the profile information and the profile owner identifier thatis identifiable to the second profile server in the first profile owneridentifier is the same as the profile owner identifier that isidentifiable to the second profile server in the profile information, itis determined that the first profile owner identifier is the same as thesecond profile owner identifier.

S405. The first profile server sends an RPM command to the userequipment when the first profile owner identifier is the same as thesecond profile owner identifier, where the RPM command carries the firstprofile owner identifier, the EID, and the ICCID.

S406. The first profile server sends a response message to the RPMserver when the first profile owner identifier is different from thesecond profile owner identifier, where the response message is used tonotify the RPM server of a verification error.

S407. After receiving the RPM command, the user equipment determineswhether the first profile owner identifier is the same as the secondprofile owner identifier.

In an embodiment, the user equipment may first search for the secondprofile owner identifier in the profile information based on the ICCIDcarried in the RPM command, and compare the first profile owneridentifier with the second profile owner identifier to verify whetherthe first profile owner identifier is the same as the second profileowner identifier. A verification method of this embodiment is the sameas the verification method of the first profile server in S404. Detailsare not described herein again for the sake of brevity.

S408. The user equipment executes the RPM command when the first profileowner identifier is the same as the second profile owner identifier; orthe user equipment may send a response message to the first profileserver or the RPM server when the first profile owner identifier isdifferent from the second profile owner identifier, where the responsemessage is used to notify the RPM server of a verification error.

In this embodiment, when the first profile server configured to managethe profile and the second profile server configured to download theprofile are different servers, whether the RPM server that initiates theRPM command specific to the downloaded profile is an owner of theprofile is verified; and a PO verification method is provided whendifferent PO IDs are used by the two profile servers to identify a samePO. This not only prevents a third party from maliciously tampering withprofile information that is not possessed by the third party, but alsoavoids a loss caused to an operator or a profile owner due to a user'saccess to an invalid network or random profile unlocking. In addition,the profile server verifies the PO on a network side. In this way,network security can be improved, a bidirectional authentication processbetween the profile server and a terminal can be reduced, and a waste ofnetwork resources can be reduced.

FIG. 5A and FIG. 5B are a schematic flowchart of an informationverification method according to still another embodiment. In thisembodiment, a first profile server configured to manage a profile and asecond profile server configured to download the profile are differentservers. The method includes but is not limited to the following steps.

S501. An RPM server or the second profile server updates profileinformation to user equipment. This step includes: S501 a. The RPMserver sends an update message to the user equipment. S501 b. The secondprofile server sends an update message to the user equipment. The updatemessage includes an identifier of the first profile server, and mayfurther include a corresponding profile owner identifier.

In an embodiment, the RPM server or the second profile server maypreconfigure information about the first profile server in the profileinformation, and preconfigure a profile owner identifier that isidentifiable to the first profile server. The information about thefirst profile server may include the identifier of the first profileserver.

After the foregoing information is configured, the user equipment may beassigned to the first profile server for remote profile management.Therefore, the RPM server or the second profile server may send theupdate message to the user equipment. PO IDs of a same profile owner maybe the same or different. Therefore, the PO IDs also need to be updatedto the profile information. For example, if a PO ID assigned by a firstSM DP+ to China Mobile is 46001, and a PO ID assigned by a second SM DP+to China Mobile is CMCC, an identifier of the first SM DP+ and thecorresponding identifier 46001 of China Mobile are stored in the profileinformation, and an identifier of the second SM DP+ and thecorresponding identifier CMCC of China Mobile are also stored in theprofile information, to subsequently search for and verify the PO. Afterreceiving the update message, the user equipment updates the identifierof the first profile server and the corresponding profile owneridentifier to the profile information. Optionally, the RPM server mayfurther configure the identifier of the first profile server and thecorresponding profile owner identifier in the profile information of theuser equipment by using an OTA message.

Optionally, after receiving the update request sent by the RPM server orthe second profile server, the user equipment may verify identityvalidity of the RPM server or the second profile server based on the POID carried in the update request. In an embodiment, verification oridentification may be performed based on information such as a messageheader field and an initiator certificate that are in the update messageand that are used to identify an initiator, and the PO ID that iscarried in the update message. For example, if the PO ID carried in theupdate request is the PO ID of China Mobile, it is verified whether theinitiator of the update request is China Mobile. If the initiator of theupdate request is not China Mobile, it is verified that an identity ofthe initiator is invalid. If China Mobile is the initiator of the updaterequest, it is verified that the identity of the initiator is valid.Further, the identifier of the first profile server and thecorresponding profile owner identifier are updated to the local profileinformation. This prevents a third party from maliciously using the POID of China Mobile to manage the profile. In verification on theidentity of the initiator, a verification operation of determiningwhether the initiator is a valid initiator, a verification operation ofjudging whether the initiator is a valid initiator, or the like may beperformed.

S502. The RPM server sends an RPM request to the first profile server,where the RPM request includes a first PO ID, and the RPM requestfurther includes at least one of an EID, an ICCID, and RPMcommand-related information, and the first profile owner identifierincludes at least one of the following: a profile owner identifier thatis identifiable to the first profile server or a profile owneridentifier that is identifiable to the second profile server.

The profile owner identifier may vary with a implementation. Forexample, an MNO and an SM DP+ may agree on a profile owner identifier inadvance, or an MNO and an SM DP+ may use an identifier of a messageinitiator between the MNO and the SM DP+ as a profile owner identifier.For another example, State Grid, serving as a company, manages a profilepurchased by State Grid from the MNO. In this case, the first profileowner identifier may include a PO ID assigned by the MNO or the SM DP+to State Grid. Alternatively, a mobile virtual network operatorpurchases a profile from the MNO. In this case, the first profile owneridentifier may include a PO ID assigned to the MVNO. This ensures thatState Grid or the MVNO manages the profile of State Grid or the MVNO byusing the MNO.

Optionally, after receiving the RPM request initiated by the RPM server,the first profile server may verify identity validity of the RPM serverbased on the PO ID carried in the RPM request. In an embodiment,verification or identification may be performed based on informationsuch as a message header field and an initiator certificate that are inthe message sent by the RPM server to the first profile server and thatare used to identify an initiator, and the PO ID that is carried in theRPM request. For example, if the PO ID carried in the RPM request is aPO ID of China Mobile, it is verified whether the initiator of the RPMrequest is China Mobile. If the initiator of the RPM request is notChina Mobile, it is verified that the identity of the initiator isinvalid. If the initiator of the RPM request is China Mobile, it isverified that the identity of the initiator is valid. This prevents athird party from maliciously using the PO ID of China Mobile to managethe profile. In verification on the identity of the initiator, averification operation of determining whether the initiator is a validinitiator, a verification operation of judging whether the initiator isa valid initiator, or the like may be performed.

S503. The first profile server obtains a second profile owner identifierin profile information, where the second profile owner identifierincludes at least one of the following: a profile owner identifier thatis identifiable to the first profile server or a profile owneridentifier that is identifiable to the second profile server. Thefollowing two optional manners are included.

The first implementation includes the following steps:

S503 a. The first profile server may send a first request to the userequipment, where the first request is used to obtain the second profileowner identifier, and the first request may be a Get ProfileInfointerface command, and may carry at least one of an identifier of thesecond profile server, an EID, and an ICCID. In an embodiment, after asecure channel is established between the first profile server and theuser equipment, the first profile server may send the first request tothe user equipment through an ES 8+ or ES 9+ interface between the firstprofile server and the user equipment.

S503 b. After receiving the first request, the user equipment searchesfor the corresponding profile information based on the ICCID carried inthe RPM request, and after finding the corresponding profileinformation, the user equipment sends, to the first profile server, theprofile information that carries the second profile owner identifier.

The second implementation includes the following steps.

S503 c. The first profile server may send a second request to the secondprofile server, where the second request is used to obtain the secondprofile owner identifier, and the second request may be a GetProfileInfo interface command, and may carry at least one of anidentifier of the second profile server, an EID, and an ICCID. Theidentifier of the second profile server is used to perform addressing onthe corresponding second profile server, and the EID or the ICCID isused to search for a PO to which the corresponding profile belongs, toobtain the PO ID. For example, the PO may be read from the profileinformation stored in the second profile server, or the second profileserver maintains a plurality of profiles of the RPM server, and searchesfor, based on the ICCID carried in the second request, a PO to which thecorresponding profile belongs, to obtain the PO ID.

S503 d. After obtaining the second profile owner identifiercorresponding to the PO, the second profile server sends, to the firstprofile server, the second profile owner identifier or the profileinformation that carries the second profile owner identifier.

S504. The first profile server determines whether the first profileowner identifier is the same as the second profile owner identifier.

In an embodiment, the first profile server may compare the first profileowner identifier with the second profile owner identifier to verify ordetermine whether the first profile owner identifier is the same as thesecond profile owner identifier.

S505. The first profile server sends an RPM command to the userequipment when the first profile owner identifier is the same as thesecond profile owner identifier, where the RPM command carries the firstprofile owner identifier, the EID, and the ICCID.

It can be noted that the first profile owner identifier includes atleast one of the following: a profile owner identifier that isidentifiable to the first profile server or a profile owner identifierthat is identifiable to the second profile server. The second profileowner identifier also includes at least one of the following: a profileowner identifier that is identifiable to the first profile server or aprofile owner identifier that is identifiable to the second profileserver. Although the profile owner identifier that is identifiable tothe first profile server and the profile owner identifier that isidentifiable to the second profile server are PO IDs of a same PO, theprofile owner identifier that is identifiable to the first profileserver and the profile owner identifier that is identifiable to thesecond profile server may be different. Therefore, the first profileserver may verify that the profile owner identifier that is identifiableto the first profile server and the profile owner identifier that isidentifiable to the second profile server are different. Furtherverification needs to be performed in the following manner.

S506. The first profile server obtains an identifier correspondence listwhen the first profile owner identifier is different from the secondprofile owner identifier.

In an embodiment, the first profile server may obtain the identifiercorrespondence list from the RPM server; obtain the identifiercorrespondence list from the second profile server; or obtain theidentifier correspondence list from the local memory. The identifiercorrespondence list includes a correspondence between a profile serveridentifier corresponding to a profile owner and a profile owneridentifier. For example, if a PO ID assigned by a first SM DP+ to ChinaMobile is 46001, and a PO ID assigned by a second SM DP+ is CMCC, anidentifier of the first SM DP+ and the corresponding identifier 46001 ofChina Mobile are stored in the identifier correspondence list, and anidentifier of the second SM DP+ and the corresponding identifier CMCC ofChina Mobile are also stored in the identifier correspondence list, tosearch for and verify the PO.

S507. The first profile server determines whether a profile owneridentifier corresponding to the first profile owner identifier exists inthe identifier correspondence list.

In an embodiment, the profile owner identifier that is identifiable tothe first profile server or the profile owner identifier that isidentifiable to the second profile server may be separately comparedwith a profile owner identifier in the identifier correspondence list,to determine whether the profile owner identifier corresponding to thefirst profile owner identifier exists in the identifier correspondinglist.

S508. The first profile server sends the RPM command to the userequipment when the profile owner identifier corresponding to the firstprofile owner identifier exists in the identifier correspondence list.

S509. The first profile server sends a response message to the RPMserver when the profile owner identifier corresponding to the firstprofile owner identifier does not exist in the identifier correspondencelist, where the response message is used to notify the RPM server of averification error.

S510. After receiving the RPM command, the user equipment determineswhether the first profile owner identifier is the same as the secondprofile owner identifier.

In an embodiment, the user equipment may first search for the secondprofile owner identifier in the profile information based on the ICCIDcarried in the RPM command, and compare the first profile owneridentifier with the second profile owner identifier to verify whetherthe first profile owner identifier is the same as the second profileowner identifier. A verification method of this embodiment is the sameas the verification method of the first profile server in S504 to S507.Details are not described herein for the sake of brevity.

S511. The user equipment executes the RPM command when the first profileowner identifier is the same as the second profile owner identifier; orthe user equipment may send a response message to the first profileserver or the RPM server when the first profile owner identifier isdifferent from the second profile owner identifier, where the responsemessage is used to notify the RPM server of a verification error.

In this embodiment, when the first profile server configured to managethe profile and the second profile server configured to download theprofile are different servers, whether the RPM server that initiates theRPM command specific to the downloaded profile is an owner of theprofile is verified; and a PO verification method is provided whendifferent PO IDs are used by the two profile servers to identify a samePO. In addition, based on the foregoing embodiment, for the identifiercorrespondence list maintained by the profile server, when verifyingthat the first profile owner identifier is different from the secondprofile owner identifier, the first profile server may further verify,based on the correspondence list, whether the PO IDs belong to a sameprofile owner. This not only prevents a third party from maliciouslytampering with profile information that is not possessed by the thirdparty, but also avoids a loss caused to an operator or a profile ownerdue to a user's access to an invalid network or random profileunlocking. In addition, the profile server verifies the PO on a networkside. In this way, network security can be improved, a bidirectionalauthentication process between the profile server and a terminal can bereduced, and a waste of network resources can be reduced.

FIG. 6 is a schematic flowchart of an information verification methodaccording to yet another embodiment. In this embodiment, a first profileserver configured to manage a profile and a second profile serverconfigured to download the profile are different servers. The methodincludes but is not limited to the following steps.

S601. An RPM server or the second profile server updates profileinformation to user equipment. This step includes: S601 a. The RPMserver sends an update message to the user equipment. S601 b. The secondprofile server sends an update message to the user equipment. The updatemessage includes an identifier of the first profile server, and mayfurther include a corresponding profile owner identifier.

In an embodiment, the RPM server or the second profile server maypreconfigure information about the first profile server in the profileinformation, and preconfigure a profile owner identifier that isidentifiable to the first profile server. The information about thefirst profile server may include the identifier of the first profileserver.

After the foregoing information is configured, the user equipment may beassigned to the first profile server for remote profile management.Therefore, the RPM server or the second profile server may send theupdate message to the user equipment. PO IDs of a same profile owner maybe the same or different. Therefore, the PO IDs also need to be updatedto the profile information. For example, if a PO ID assigned by a firstSM DP+ to China Mobile is 46001, and a PO ID assigned by a second SM DP+is CMCC, an identifier of the first SM DP+ and the correspondingidentifier 46001 of China Mobile are stored in the profile information,and the identifier of the second SM DP+ and the corresponding identifierCMCC of China Mobile are also stored in the profile information, tosubsequently search for and verify the PO. After receiving the updatemessage, the user equipment updates the identifier of the first profileserver and the corresponding profile owner identifier to the profileinformation. Optionally, the RPM server may further configure theidentifier of the first profile server and the corresponding profileowner identifier in the profile information of the user equipment byusing an OTA message.

Optionally, after receiving the update request sent by the RPM server orthe second profile server, the user equipment may verify identityvalidity of the RPM server or the second profile server based on the POID carried in the update request. In an embodiment, verification oridentification may be performed by using information such as a messageheader field and an initiator certificate that are in the update messageand that are used to identify an initiator, and the PO ID that iscarried in the update message. For example, if the PO ID carried in theupdate request is the PO ID of China Mobile, it is verified whether theinitiator of the update request is China Mobile. If the initiator of theupdate request is not China Mobile, it is verified that an identity ofthe initiator is invalid. If the initiator of the update request isChina Mobile, it is verified that the identity of the initiator isvalid. Further, the identifier of the first profile server and thecorresponding profile owner identifier are updated to the local profileinformation. This prevents a third party from maliciously using the POID of China Mobile to manage the profile.

S602. The RPM server may determine whether the first profile serverconfigured to manage the profile and the second profile serverpreviously configured to download the profile are a same server. Whenthe first profile server and the second profile server are differentservers, the RPM server determines a profile owner identifier that isidentifiable to the first profile server or a profile owner identifierthat is identifiable to the second profile server. Although the profileowner identifier that is identifiable to the first profile server andthe profile owner identifier that is identifiable to the second profileserver are PO IDs of a same PO, the profile owner identifier that isidentifiable to the first profile server and the profile owneridentifier that is identifiable to the second profile server may bedifferent. Therefore, a correspondence between the identifier of thefirst profile server and the profile owner identifier and acorrespondence between the identifier of the second profile server andthe profile owner identifier are separately established.

S603. The RPM server sends an RPM request to the first profile server.The RPM request includes a first PO ID, and the RPM request furtherincludes at least one of an EID, an ICCID, or RPM command-relatedinformation.

The first profile owner identifier includes at least one of thefollowing: a profile owner identifier that is identifiable to the firstprofile server or a profile owner identifier that is identifiable to thesecond profile server. Further, the first profile owner identifier mayinclude a profile server identifier and a profile owner identifier,including the identifier of the first profile server and thecorresponding profile owner identifier that is identifiable to the firstprofile server, or the identifier of the second profile server and thecorresponding profile owner identifier that is identifiable to thesecond profile server.

In addition, the profile owner identifier may vary with aimplementation. For example, an MNO and an SM DP+ may agree on a profileowner identifier in advance, or an MNO and an SM DP+ may use anidentifier of a message initiator between the MNO and the SM DP+ as aprofile owner identifier. For another example, State Grid, serving as acompany, manages a profile purchased by State Grid from the MNO. In thiscase, the first profile owner identifier may include a PO ID assigned bythe MNO or the SM DP+ to State Grid. Alternatively, a MVNO purchases aprofile from the MNO. In this case, the first profile owner identifiermay include a PO ID assigned to the MVNO. This ensures that State Gridor the MVNO manages the profile of State Grid or the MVNO by using theMNO.

Optionally, after receiving the RPM request initiated by the RPM server,the first profile server may verify identity validity of the RPM serverbased on the PO ID carried in the RPM request. In an embodiment,verification or identification may be performed by using informationsuch as a message header field and an initiator certificate that are inthe message sent by the RPM server to the first profile server and thatare used to identify an initiator, and the PO ID that is carried in theRPM request. For example, if the PO ID carried in the RPM request is aPO ID of China Mobile, it is verified whether the initiator of the RPMrequest is China Mobile. If the initiator of the RPM request is notChina Mobile, it is verified that an identity of the initiator isinvalid. If the initiator of the RPM request is China Mobile, it isverified that the identity of the initiator is valid. This prevents athird party from maliciously using the PO ID of China Mobile to managethe profile. In verification on the identity of the initiator, averification operation of determining whether the initiator is a validinitiator, a verification operation of judging whether the initiator isa valid initiator, or the like may be performed.

S604. The first profile server obtains a second profile owner identifierin profile information. The second profile owner identifier includes atleast one of the following: a profile owner identifier that isidentifiable to the first profile server or a profile owner identifierthat is identifiable to the second profile server. The following twooptional manners are included.

The first implementation includes the following steps:

S604 a. The first profile server may send a first request to the userequipment, where the first request is used to obtain the second profileowner identifier, and the first request may be a Get ProfileInfointerface command, and may carry at least one of the identifier of thesecond profile server, an EID, and an ICCID. In an embodiment, after asecure channel is established between the first profile server and theuser equipment, the first profile server may send the first request tothe user equipment through an ES 8+ or ES 9+ interface between the firstprofile server and the user equipment.

S604 b. After receiving the first request, the user equipment searchesfor the corresponding profile information based on the ICCID carried inthe RPM request, and after finding the corresponding profileinformation, the user equipment sends, to the first profile server, theprofile information that carries the second profile owner identifier.

The second implementation includes the following steps.

S604 c. The first profile server may send a second request to the secondprofile server, where the second request is used to obtain the secondprofile owner identifier, and the second request may be a GetProfileInfo interface command, and may carry at least one of theidentifier of the second profile server, an EID, and an ICCID. Theidentifier of the second profile server is used to perform addressing onthe corresponding second profile server, and the EID or the ICCID isused to search for a PO to which the corresponding profile belongs, toobtain the PO ID. For example, the PO may be read from the profileinformation stored in the second profile server, or the second profileserver maintains a plurality of profiles of the RPM server, and searchesfor, based on the ICCID carried in the second request, a PO to which thecorresponding profile belongs, to obtain the PO ID.

S604 d. After obtaining the second profile owner identifiercorresponding to the PO, the second profile server sends, to the firstprofile server, the profile information that carries the second profileowner identifier.

In this embodiment, because the first profile owner identifier includesa profile server identifier and a profile owner identifier, the secondprofile owner identifier that is identifiable to the first profileserver in the profile information may be obtained based on theidentifier of the first profile server included in the first profileowner identifier. Alternatively, the second profile owner identifierthat is identifiable to the second profile server in the profileinformation is obtained based on the identifier of the second profileserver included in the first profile owner identifier.

S605. The first profile server determines whether the first profileowner identifier is the same as the second profile owner identifier.

In an embodiment, the first profile server may compare the first profileowner identifier with the second profile owner identifier to verify ordetermine whether the first profile owner identifier is the same as thesecond profile owner identifier.

S606. The first profile server sends an RPM command to the userequipment when the first profile owner identifier is the same as thesecond profile owner identifier, where the RPM command carries the firstprofile owner identifier, the EID, and the ICCID.

S607. The first profile server sends a response message to the RPMserver when the first profile owner identifier is different from thesecond profile owner identifier, where the response message is used tonotify the RPM server of a verification error.

S608. After receiving the RPM command, the user equipment determineswhether the first profile owner identifier is the same as the secondprofile owner identifier.

In an embodiment, the user equipment may first search for the secondprofile owner identifier in the profile information based on the ICCIDcarried in the RPM command, and compare the first profile owneridentifier with the second profile owner identifier to verify ordetermine whether the first profile owner identifier is the same as thesecond profile owner identifier. A verification method of thisembodiment is the same as the verification method of the first profileserver in S605. Details are not described herein for the sake ofbrevity.

S609. The user equipment executes the RPM command when the first profileowner identifier is the same as the second profile owner identifier; orthe user equipment may send a response message to the first profileserver or the RPM server when the first profile owner identifier isdifferent from the second profile owner identifier, where the responsemessage is used to notify the RPM server of a verification error.

In this embodiment, when the first profile server configured to managethe profile and the second profile server configured to download theprofile are different servers, whether the RPM server that initiates theRPM command specific to the downloaded profile is an owner of theprofile is verified; and a PO verification method is provided whendifferent PO IDs are used by the two profile servers to identify a samePO. In addition, the RPM server determines the profile owner identifierthat is identifiable to the first profile server or the profile owneridentifier that is identifiable to the second profile server, so thatthe first profile server obtains a corresponding profile owneridentifier for verification. This not only prevents a third party frommaliciously tampering with profile information that is not possessed bythe third party, but also avoids a loss caused to an operator or aprofile owner due to a user's access to an invalid network or randomprofile unlocking. In addition, the profile server verifies the PO on anetwork side. In this way, network security can be improved, abidirectional authentication process between the profile server and aterminal can be reduced, and a waste of network resources can bereduced.

The foregoing describes in detail the methods in the embodiments. Thefollowing provides apparatuses in the embodiments.

FIG. 7 is a schematic structural diagram of a first profile serveraccording to an embodiment. The first profile server may include areceiving module 701, an obtaining module 702, a processing module 703,and a sending module 704. Detailed descriptions of the modules are asfollows:

The receiving module 701 is configured to receive an RPM request sent byan RPM server, where the RPM request includes a first profile owneridentifier.

The obtaining module 702 is configured to obtain a second profile owneridentifier in profile information.

The processing module 703 is configured to determine whether the firstprofile owner identifier is the same as the second profile owneridentifier.

The sending module 704 is configured to send an RPM command to userequipment when the first profile owner identifier is the same as thesecond profile owner identifier.

Optionally, the obtaining module 702 is configured to obtain the secondprofile owner identifier in the profile information from a local memory.

Optionally, the obtaining module 702 is configured to: send a firstrequest to the user equipment, where the first request is used to obtainthe second profile owner identifier; and receive the profile informationthat is sent by the user equipment and that carries the second profileowner identifier.

Optionally, the obtaining module 702 is configured to: send a secondrequest to a second profile server, where the second request is used toobtain the second profile owner identifier; and receive the profileinformation that is sent by the second profile server and that carriesthe second profile owner identifier.

Optionally, the first profile owner identifier and the second profileowner identifier each include at least one of the following: a profileowner identifier that is identifiable to the first profile server or aprofile owner identifier that is identifiable to the second profileserver.

Optionally, the obtaining module 702 is further configured to obtain anidentifier correspondence list when the first profile owner identifieris different from the second profile owner identifier, where theidentifier correspondence list includes a correspondence between aprofile server identifier and a profile owner identifier; the processingmodule 703 is further configured to determine whether a profile owneridentifier corresponding to the first profile owner identifier exists inthe identifier correspondence list; and the sending module 704 isfurther configured to send the RPM command to the user equipment whenthe profile owner identifier corresponding to the first profile owneridentifier exists in the identifier correspondence list.

Optionally, the obtaining module 702 is configured to: obtain theidentifier correspondence list from the RPM server; obtain theidentifier correspondence list from the second profile server; or obtainthe identifier correspondence list from the local memory.

Optionally, the first profile server is a server configured to manage aprofile, and the second profile server is a server configured todownload the profile.

Optionally, the profile owner identifier includes a profile serveridentifier and a profile owner identifier.

It can be noted that, for implementation of the modules, refer tocorresponding descriptions of the method embodiments shown in FIG. 3 toFIG. 6. The modules perform the methods and the functions performed bythe first profile server in the foregoing embodiments.

FIG. 8 is a schematic structural diagram of user equipment according toan embodiment. The user equipment may include a receiving module 801, anobtaining module 802, a processing module 803, and an execution module804. Detailed descriptions of the modules are as follows:

The receiving module 801 is configured to receive an RPM command sent bya first profile server, where the RPM command includes a first profileowner identifier.

The obtaining module 802 is configured to obtain a second profile owneridentifier in profile information.

The processing module 803 is configured to determine whether the firstprofile owner identifier is the same as the second profile owneridentifier.

The execution module 804 is configured to execute the RPM command whenthe first profile owner identifier is the same as the second profileowner identifier.

Optionally, the receiving module 801 is further configured to receive anupdate message sent by an RPM server or a second profile server, wherethe update message includes an identifier of the first profile serverand a corresponding profile owner identifier.

Optionally, the first profile owner identifier includes at least one ofthe following: a profile owner identifier that is identifiable to thefirst profile server or a profile owner identifier that is identifiableto the second profile server.

Optionally, the obtaining module 802 is further configured to obtain anidentifier correspondence list when the first profile owner identifieris different from the second profile owner identifier, where theidentifier correspondence list includes a correspondence between aprofile server identifier and a profile owner identifier; the processingmodule 803 is further configured to determine whether a profile owneridentifier corresponding to the first profile owner identifier exists inthe identifier correspondence list; and the execution module 804 isfurther configured to execute the RPM command when the profile owneridentifier corresponding to the first profile owner identifier exists inthe identifier correspondence list.

Optionally, the receiving module 801 is further configured to receive afirst request sent by the first profile server, where the first requestis used to obtain the second profile owner identifier; and the sendingmodule 805 is configured to send, to the first profile server, theprofile information that carries the second profile owner identifier.

It can be noted that, for implementation of the modules, refer tocorresponding descriptions of the method embodiments shown in FIG. 3 toFIG. 6. The modules perform the methods and the functions performed bythe user equipment in the foregoing embodiments.

FIG. 9 is a schematic structural diagram of an RPM server according toan embodiment. The RPM server may include a sending module 901 and aprocessing module 902. Detailed descriptions of the modules are asfollows:

The sending module 901 is configured to send an RPM request to a firstprofile server, where the RPM request includes a first profile owneridentifier, and the RPM request is used to instruct the first profileserver to determine whether a second profile owner identifier in profileinformation is the same as the first profile owner identifier; and sendan RPM command to user equipment when the second profile owneridentifier is the same as the first profile owner identifier.

Optionally, the processing module 902 is configured to: determinewhether the first profile server configured to manage a profile and asecond profile server previously configured to download the profile area same server; and when the first profile server and the second profileserver are different servers, determine a profile owner identifier thatis identifiable to the first profile server or a profile owneridentifier that is identifiable to the second profile server.

It can be noted that, for implementation of the modules, refer tocorresponding descriptions of the method embodiments shown in FIG. 3 toFIG. 6. The modules perform the methods and the functions performed bythe RPM server in the foregoing embodiments.

FIG. 10 is a schematic structural diagram of another first profileserver according to an embodiment. As shown in the figure, the firstprofile server may include at least one processor 1001, at least onecommunications interface 1002, at least one memory 1003, and at leastone communications bus 1004.

The processor 1001 may be a central processing unit, a general-purposeprocessor, a digital signal processor, an application-specificintegrated circuit, a field programmable gate array or anotherprogrammable logical device, a transistor logical device, a hardwarecomponent, or any combination thereof. The processor 1001 may implementor execute various example logical blocks, modules, and circuitsdescribed with reference to content disclosed in am embodiment.Alternatively, the processor may be a combination of processorsimplementing a computing function, for example, a combination of one ormore microprocessors, or a combination of a digital signal processor anda microprocessor. The communications bus 1004 may be a peripheralcomponent interconnect PCI bus, an extended industry standardarchitecture EISA bus, or the like. The bus may be classified into anaddress bus, a data bus, a control bus, or the like. For ease ofrepresentation, only one thick line is used to represent the bus in FIG.10, but this does not mean that there is only one bus or only one typeof bus. The communications bus 1004 is configured to implementconnection and communication between these components. Thecommunications interface 1002 in the device in this embodiment isconfigured to perform signaling or data communication with another nodedevice. The memory 1003 may include a volatile memory such as anonvolatile random access memory (NVRAM), a phase change random accessmemory (PRAM), or a magnetoresistive random access memory (MRAM), or mayinclude a nonvolatile memory such as at least one magnetic disk storagedevice, an electrically erasable programmable read-only memory (EEPROM),a flash storage device such as a NOR flash memory (NOR flash memory) ora NAND flash memory, a semiconductor such as a solid state disk (SSD),or the like. Optionally, the memory 1003 may be at least one storageapparatus far away from the processor 1001. The memory 1003 stores agroup of program code, and the processor 1001 executes a program in thememory 1003 that is executed by the foregoing first profile server.

An RPM request sent by an RPM server is received by using thecommunications interface 1002, and the RPM request includes a firstprofile owner identifier;

a second profile owner identifier in profile information is obtained;

it is determined whether the first profile owner identifier is the sameas the second profile owner identifier; and

an RPM command is sent by using the communications interface 1002 touser equipment when the first profile owner identifier is the same asthe second profile owner identifier.

Optionally, the processor 1001 is further configured to perform thefollowing operation:

obtaining the second profile owner identifier in the profile informationfrom a local memory.

Optionally, the processor 1001 is further configured to perform thefollowing operations:

sending a first request to the user equipment by using thecommunications interface 1002, where the first request is used to obtainthe second profile owner identifier; and

receiving, by using the communications interface 1002, the profileinformation that is sent by the user equipment and that carries thesecond profile owner identifier.

Optionally, the processor 1001 is further configured to perform thefollowing operations:

sending a second request to a second profile server by using thecommunications interface 1002, where the second request is used toobtain the second profile owner identifier; and

receiving, by using the communications interface 1002, the profileinformation that is sent by the second profile server and that carriesthe second profile owner identifier.

The first profile owner identifier and the second profile owneridentifier each include at least one of the following: a profile owneridentifier that is identifiable to the first profile server or a profileowner identifier that is identifiable to the second profile server.

Optionally, the processor 1001 is further configured to perform thefollowing operations:

obtaining an identifier correspondence list when the first profile owneridentifier is different from the second profile owner identifier, wherethe identifier correspondence list includes a correspondence between aprofile server identifier and a profile owner identifier;

determining whether a profile owner identifier corresponding to thefirst profile owner identifier exists in the identifier correspondencelist; and

when a profile owner identifier corresponding to the first profile owneridentifier exists in the identifier correspondence list, sending the RPMcommand to the user equipment by using the communications interface1002.

Optionally, the processor 1001 is further configured to perform thefollowing operations:

obtaining the identifier correspondence list from the RPM server;

obtaining the identifier correspondence list from the second profileserver; or obtaining the identifier correspondence list from the localmemory.

The first profile server is a server configured to manage a profile, andthe second profile server is a server configured to download theprofile.

The profile owner identifier includes a profile server identifier and aprofile owner identifier.

Further, the processor may further cooperate with the memory and thecommunications interface to perform the operations of the first profileserver in the foregoing embodiments.

FIG. 11 is a schematic structural diagram of other user equipmentaccording to an embodiment. As shown in the figure, the user equipmentmay include at least one processor 1101, at least one communicationsinterface 1102, at least one memory 1103, and at least onecommunications bus 1104.

The processor 1101 may be the various types of processors mentionedabove. The communications bus 1104 may be a peripheral componentinterconnect PCI bus, an extended industry standard architecture EISAbus, or the like. The bus may be classified into an address bus, a databus, a control bus, or the like. For ease of representation, only onethick line is used to represent the bus in FIG. 11, but this does notmean that there is only one bus or only one type of bus. Thecommunications bus 1104 is configured to implement connection andcommunication between these components. The communications interface1102 in the device in this embodiment is configured to perform signalingor data communication with another node device. The memory 1103 may bethe various types of memories mentioned above. Optionally, the memory1103 may be at least one storage apparatus far away from the processor1101. The memory 1103 stores a group of program code, and the processor1101 executes a program in the memory 1103 that is executed by theforegoing user equipment.

An RPM command sent by a first profile server is received by using thecommunications interface 1102, where the RPM command includes a firstprofile owner identifier;

a second profile owner identifier in profile information is obtained;

it is determined whether the first profile owner identifier is the sameas the second profile owner identifier; and

the RPM command is executed when the first profile owner identifier isthe same as the second profile owner identifier.

Optionally, the processor 1101 is further configured to perform thefollowing operation:

receiving, by using the communications interface 1102, an update messagesent by an RPM server or a second profile server, where the updatemessage includes an identifier of the first profile server and acorresponding profile owner identifier.

The first profile owner identifier includes at least one of thefollowing: a profile owner identifier that is identifiable to the firstprofile server or a profile owner identifier that is identifiable to thesecond profile server.

Optionally, the processor 1101 is further configured to perform thefollowing operation:

obtaining an identifier correspondence list when the first profile owneridentifier is different from the second profile owner identifier, wherethe identifier correspondence list includes a correspondence between aprofile server identifier and a profile owner identifier;

determining whether a profile owner identifier corresponding to thefirst profile owner identifier exists in the identifier correspondencelist; and

executing the RPM command when the profile owner identifiercorresponding to the first profile owner identifier exists in theidentifier correspondence list.

Optionally, the processor 1101 is further configured to perform thefollowing operations:

receiving, by using the communications interface 1102, a first requestsent by the first profile server, where the first request is used toobtain the second profile owner identifier; and

sending, to the first profile server by using the communicationsinterface 1102, the profile information that carries the second profileowner identifier.

Further, the processor may further cooperate with the memory and thecommunications interface to perform the operations of the user equipmentin the foregoing embodiments.

FIG. 12 is a schematic structural diagram of another RPM serveraccording to an embodiment. As shown in the figure, the RPM server mayinclude at least one processor 1201, at least one communicationsinterface 1202, at least one memory 1203, and at least onecommunications bus 1204.

The processor 1201 may be the various types of processors mentionedabove. The communications bus 1204 may be a peripheral componentinterconnect PCI bus, an extended industry standard architecture EISAbus, or the like. The bus may be classified into an address bus, a databus, a control bus, or the like. For ease of representation, only onethick line is used to represent the bus in FIG. 12, but this does notmean that there is only one bus or only one type of bus. Thecommunications bus 1204 is configured to implement connection andcommunication between these components. The communications interface1202 in the device in this embodiment is configured to perform signalingor data communication with another node device. The memory 1203 may bethe various types of memories mentioned above. Optionally, the memory1203 may be at least one storage apparatus far away from the processor1201. The memory 1203 stores a group of program code, and the processor1201 executes a program in the memory 1203 that is executed by theforegoing RPM server.

An RPM request is sent to a first profile server by using thecommunications interface 1202, where the RPM request includes a firstprofile owner identifier, and the RPM request is used to instruct thefirst profile server to determine whether a second profile owneridentifier in profile information is the same as the first profile owneridentifier; and an RPM command is sent to user equipment when the secondprofile owner identifier is the same as the first profile owneridentifier.

Optionally, the processor 1201 is further configured to perform thefollowing operations:

determining whether the first profile server configured to manage aprofile and a second profile server previously configured to downloadthe profile are a same server; and

when the first profile server and the second profile server aredifferent servers, determining a profile owner identifier that isidentifiable to the first profile server or a profile owner identifierthat is identifiable to the second profile server.

Further, the processor may further cooperate with the memory and thecommunications interface to perform the operations of the RPM server inthe foregoing embodiments.

All or some of the foregoing embodiments may be implemented by usingsoftware, hardware, firmware, or any combination thereof. When softwareis used to implement the embodiments, all or some of the embodiments maybe implemented in a form of a computer program product. The computerprogram product includes one or more computer instructions. When thecomputer program instructions are loaded and executed on a computer, theprocedure or functions according to the embodiments are all or partiallygenerated. The computer may be a general-purpose computer, a dedicatedcomputer, a computer network, or other programmable apparatuses. Thecomputer instructions may be stored in a computer-readable storagemedium or may be transmitted from a computer-readable storage medium toanother computer-readable storage medium. For example, the computerinstructions may be transmitted from a website, computer, server, ordata center to another website, computer, server, or data center in awired (for example, a coaxial cable, an optical fiber, or a digitalsubscriber line (DSL)) or wireless (for example, infrared, radio, ormicrowave) manner. The computer-readable storage medium may be anyusable medium accessible by a computer, or a data storage device, suchas a server or a data center, integrating one or more usable media. Theusable medium may be a magnetic medium (for example, a floppy disk, ahard disk, or a magnetic tape), an optical medium (for example, a DVD),a semiconductor medium (for example, an SSD), or the like.

The objectives, technical solutions, and beneficial effects of theinvention have been described in more detail with reference to theforegoing embodiments. Any modification, equivalent replacement, orimprovement made without departing from the spirit and principle of theinvention shall fall within the protection scope of the invention.

1-37. (canceled)
 38. An information verification method comprising:receiving, by a first profile server, a remote profile managementrequest sent by a remote profile management server, wherein the remoteprofile management request comprises a first profile owner identifier;obtaining, by the first profile server, a second profile owneridentifier in profile information; determining, by the first profileserver, whether the first profile owner identifier is the same as thesecond profile owner identifier; and sending, by the first profileserver, a remote profile management command to a user equipment when thefirst profile owner identifier is the same as the second profile owneridentifier.
 39. The method according to claim 38, wherein the obtaining,by the first profile server, of the second profile owner identifier inthe profile information further comprises: obtaining, by the firstprofile server, the second profile owner identifier in the profileinformation from a local memory.
 40. The method according to claim 38,wherein the obtaining, by the first profile server, of the secondprofile owner identifier in the profile information further comprises:sending, by the first profile server, a first request to the userequipment, wherein the first request is used to obtain the secondprofile owner identifier; and receiving, by the first profile server,the profile information that is sent by the user equipment, and theprofile information carries the second profile owner identifier.
 41. Themethod according to claim 38, wherein the obtaining, by the firstprofile server, of the second profile owner identifier in the profileinformation further comprises: sending, by the first profile server, asecond request to a second profile server, wherein the second request isused to obtain the second profile owner identifier; and receiving, bythe first profile server, the profile information that is sent by thesecond profile server, and the profile information carries the secondprofile owner identifier.
 42. The method according to claim 38, whereineach of the first profile owner identifier and the second profile owneridentifier comprise at least one of: a profile owner identifier that isidentifiable to the first profile server; and the profile owneridentifier that is identifiable to a second profile server.
 43. Themethod according to claim 42, further comprising: obtaining, by thefirst profile server, an identifier correspondence list when the firstprofile owner identifier is different from the second profile owneridentifier, wherein the identifier correspondence list comprises acorrespondence between a profile server identifier and the profile owneridentifier; determining, by the first profile server, whether theprofile owner identifier corresponding to the first profile owneridentifier exists in the identifier correspondence list; and sending, bythe first profile server, the remote profile management command to theuser equipment when the profile owner identifier corresponding to thefirst profile owner identifier exists in the identifier correspondencelist.
 44. The method according to claim 43, wherein the obtaining, bythe first profile server, of the identifier correspondence list furthercomprises: obtaining, by the first profile server, the identifiercorrespondence list from the remote profile management server, thesecond profile server, or the local memory.
 45. The method according toclaim 38, wherein the first profile server manages a profile, and asecond profile server downloads the profile.
 46. The method according toclaim 38, wherein each of the first profile owner identifier and thesecond profile owner identifier comprises a profile server identifierand a profile owner identifier.
 47. An information verification methodcomprising: receiving, by a user equipment, a remote profile managementcommand sent by a first profile server, wherein the remote profilemanagement command comprises a first profile owner identifier;obtaining, by the user equipment, a second profile owner identifier inprofile information; determining, by the user equipment, whether thefirst profile owner identifier is the same as the second profile owneridentifier; and executing, by the user equipment, the remote profilemanagement command when the first profile owner identifier is the sameas the second profile owner identifier.
 48. The method according toclaim 47, before the receiving, by the user equipment, the remoteprofile management command sent by the first profile server, furthercomprising: receiving, by the user equipment, an update message sent bythe remote profile management server or a second profile server, whereinthe update message comprises an identifier of the first profile serverand a corresponding profile owner identifier.
 49. The method accordingto claim 47, wherein the first profile owner identifier comprises atleast one of: a profile owner identifier that is identifiable to thefirst profile server; and the profile owner identifier that isidentifiable to a second profile server.
 50. The method according toclaim 47, further comprising: obtaining, by the user equipment, anidentifier correspondence list when the first profile owner identifieris different from the second profile owner identifier, wherein theidentifier correspondence list comprises a correspondence between aprofile server identifier and a profile owner identifier; determining,by the user equipment, whether the profile owner identifiercorresponding to the first profile owner identifier exists in theidentifier correspondence list; and executing, by the user equipment,the remote profile management command when the profile owner identifiercorresponding to the first profile owner identifier exists in theidentifier correspondence list.
 51. The method according to claim 47,before the receiving, by the user equipment, the remote profilemanagement command sent by the first profile server, further comprising:receiving, by the user equipment, a first request sent by the firstprofile server, wherein the first request is used to obtain the secondprofile owner identifier; and sending, by the user equipment to thefirst profile server, the profile information that carries the secondprofile owner identifier.
 52. A first profile server, comprising amemory, a communications bus, and a processor, wherein the memory isconfigured to store program code that, when executed by the processor,causes the first profile server to perform: receiving a remote profilemanagement request sent by a remote profile management server, whereinthe remote profile management request comprises a first profile owneridentifier; obtaining a second profile owner identifier in profileinformation; determining whether the first profile owner identifier isthe same as the second profile owner identifier; and sending a remoteprofile management command to a user equipment when the first profileowner identifier is the same as the second profile owner identifier. 53.The first profile server according to claim 52, wherein the obtaining ofthe second profile owner identifier in the profile informationcomprises: obtaining the second profile owner identifier in the profileinformation from a local memory.
 54. The first profile server accordingto claim 52, wherein the obtaining of the second profile owneridentifier in the profile information comprises: sending a first requestto the user equipment, wherein the first request is used to obtain thesecond profile owner identifier; and receiving the profile informationthat is sent by the user equipment, and the profile information carriesthe second profile owner identifier.
 55. The first profile serveraccording to claim 52, wherein the obtaining of the second profile owneridentifier in the profile information comprises: sending a secondrequest to a second profile server, wherein the second request is usedto obtain the second profile owner identifier; and receiving, by thefirst profile server, the profile information that is sent by the secondprofile server, and the profile information carries the second profileowner identifier.
 56. The first profile server according to claim 52,wherein each of the first profile owner identifier and the secondprofile owner identifier comprises at least one of: a profile owneridentifier that is identifiable to the first profile server; and theprofile owner identifier that is identifiable to a second profileserver.
 57. The first profile server according to claim 56, wherein thememory configured to the store program code, when executed by theprocessor, causes the first profile server to further perform: obtainingan identifier correspondence list when the first profile owneridentifier is different from the second profile owner identifier,wherein the identifier correspondence list comprises a correspondencebetween a profile server identifier and the profile owner identifier;determining whether the profile owner identifier corresponding to thefirst profile owner identifier exists in the identifier correspondencelist; and sending the remote profile management command to the userequipment when the profile owner identifier corresponding to the firstprofile owner identifier exists in the identifier correspondence list.